Count reverse offset from the back of the geometry, not the front. #5315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Fixes a problem with distance calculations in
table
responses (reported in #5306).The reverse offset value in the PhantomNodes was being incorrectly calculated. When this value was used, and the matrix covered only a small distance, it was possible for the incorrect offset to outweigh the distances added to it, and it would end up negative..
Tasklist
Requirements / Relations
Link any requirements here. Other pull requests this PR is based on?